-
Notifications
You must be signed in to change notification settings - Fork 818
Implement stream connection for remote write #6580
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Alex Le <[email protected]>
Signed-off-by: Alex Le <[email protected]>
I am ok with this change. Lets get more feedback |
…-stream-push Signed-off-by: Alex Le <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I like the change. But I don't see any tests here. Can you please add some unit tests and integration tests?
Signed-off-by: Alex Le <[email protected]>
Signed-off-by: Alex Le <[email protected]>
Signed-off-by: Alex Le <[email protected]>
Signed-off-by: Alex Le <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we mention this in https://cortexmetrics.io/docs/configuration/v1guarantees/ as experimental feature?
And can we add a simple integration test just to ensure this works E2E?
Signed-off-by: Alex Le <[email protected]>
Signed-off-by: Alex Le <[email protected]>
Signed-off-by: Alex Le <[email protected]>
Signed-off-by: Alex Le <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
What this PR does:
Introduced stream connection for RemoteWrite endpoint. Keep stream connection open on ingester side could reduce the CPU usage on ingester to open new connection each time accepting new RemoteWrite requests.
Here is the comparison between normal connection and stream connection:
Tested with 6000 TPS
Compared to normal connection, stream connection could have 8%-9% less CPU usage.
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]